-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proc/core: implementing coredump functionality for ARM64 #1774
Conversation
190251d
to
fca60bc
Compare
fca60bc
to
223844e
Compare
be0bc33
to
5be350d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is that all tests for core are stacktrace dependent and disabled (because arm64 doesn't have functioning stacktraces) so this will have to wait for stacktraces on arm64 before being merged.
5be350d
to
4f7a571
Compare
arm64 stacktraces is almost done and there are some bugfixes work left. |
4f7a571
to
9f9cc7f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, as I said I'd wait for stacktraces before merging so we can test it. We rarely touch core so there's little risk of code rot.
@aarzilli ,kindly confirm, is stacktraces implemented? |
No. |
I mean |
9f9cc7f
to
d7c3233
Compare
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few small nits, overall looks good.
@derekparker it's long pending PR so can we do all refactoring in a new PR and let this PR go in master branch |
@ossdev07 there are merge conflicts anyways. I'd say resolve the conflicts and the feedback at the same time and push your changes. After that I will merge quickly. Sorry for the delay. |
Benchmark before: BenchmarkConditionalBreakpoints-4 1 15649407130 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 14586710018 ns/op Conditional breakpoint evaluation 1.56ms -> 1.45ms Updates go-delve#1549
Signed-off-by: ossdev07 <[email protected]>
d7c3233
to
5193adf
Compare
@derekparker Review comments are incorporated. please have a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* proc/native: optimize native.status through buffering (go-delve#1865) Benchmark before: BenchmarkConditionalBreakpoints-4 1 15649407130 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 14586710018 ns/op Conditional breakpoint evaluation 1.56ms -> 1.45ms Updates go-delve#1549 * proc/core: Review Comments Incorporated Signed-off-by: ossdev07 <[email protected]> Co-authored-by: Alessandro Arzilli <[email protected]>
* proc/native: optimize native.status through buffering (go-delve#1865) Benchmark before: BenchmarkConditionalBreakpoints-4 1 15649407130 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 14586710018 ns/op Conditional breakpoint evaluation 1.56ms -> 1.45ms Updates go-delve#1549 * proc/core: Review Comments Incorporated Signed-off-by: ossdev07 <[email protected]> Co-authored-by: Alessandro Arzilli <[email protected]>
Implementing coredump functionality for ARM64 , now it can be checked by using "dlv core " command.
Floating point registers are not handled yet, working on it.